Skip to content

build(deps): group pulumi core modules for dependabot version updates#150

Merged
pedromvgomes merged 1 commit into
mainfrom
build/group-pulumi-dependabot-updates
Jun 28, 2026
Merged

build(deps): group pulumi core modules for dependabot version updates#150
pedromvgomes merged 1 commit into
mainfrom
build/group-pulumi-dependabot-updates

Conversation

@pedromvgomes

Copy link
Copy Markdown
Contributor

Why

The pulumi core modules are released in lockstep and must move together:

  • pulumi/sdk/v3 and pulumi/pkg/v3 share an internal API — pkg's workspace/plugin.go calls plugin.NewContextWithRoot / Host.LanguageRuntime, whose signatures are defined in sdk.
  • pulumi-go-provider tracks pulumi/pkg/v3's codegen/schema types (e.g. ResourceSpec).

Bumping any one of them alone produces an unbuildable tree. That's exactly how the standalone sdk/v3 3.246.0 → 3.247.0 bump in #145 broke CI: dependabot raised sdk on its own, leaving pkg behind (signature mismatch), and even the matching pkg 3.247.0 then breaks pulumi-go-provider@v1.3.2 (no compatible release exists yet).

What

Add a dependabot groups entry that bundles the routine version updates of the three coupled modules into a single PR, so dependabot proposes a buildable set rather than an unbuildable partial bump.

groups:
  pulumi:
    applies-to: version-updates
    patterns:
      - "github.com/pulumi/pulumi"
      - "github.com/pulumi/pulumi/*"
      - "github.com/pulumi/pulumi-go-provider"

applies-to: version-updates (the default) is set explicitly: security advisories on any of these are unaffected by the group and are still raised as separate, immediate PRs. Note this does not solve the case where a CVE security-update bumps only one lockstep module — that remains a manual companion-bump moment, inherent to the coupling and not something a config can fully prevent.

Plugin SDKs (pulumi-hcloud, pulumi-cloudflare) are intentionally left out of the group — they version independently of pulumi core.

Merge Commit Message

build(deps): group pulumi core modules for dependabot version updates

https://claude.ai/code/session_017Kyd98NzojozMZ19d5UCZ2

The pulumi core modules are released in lockstep: sdk/v3 and pkg/v3 share
an internal API (plugin.NewContextWithRoot et al.), and pulumi-go-provider
tracks pulumi/pkg/v3's codegen/schema types. Bumping any one of them alone
produces an unbuildable tree — which is exactly how the standalone
sdk/v3 3.247.0 bump (#145) broke CI.

Group their routine version updates into a single PR so dependabot proposes
a buildable set. applies-to defaults to version-updates, so security
advisories on any of these are still raised as separate, immediate PRs.

Claude-Session: https://claude.ai/code/session_017Kyd98NzojozMZ19d5UCZ2
@pedromvgomes pedromvgomes merged commit eea96e2 into main Jun 28, 2026
2 checks passed
@pedromvgomes pedromvgomes deleted the build/group-pulumi-dependabot-updates branch June 28, 2026 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant